|
|
|
|
|
|
|
hands by developers having completed their tasks ahead of schedule, because that means that the programmer might wake up from her slumber and think! He despises systems with architectures because, like the truth, a project backbone will set the programmer free from his grasp. He frowns on documentation, because he knows that with better programmer documentation, his gospel won't have room to grow in the future (that is, no room for errors that could lead to lapsed schedules). |
|
|
|
|
|
|
|
|
Sharing Development Costs with Other Enterprise Business Groups |
|
|
|
|
|
|
|
|
It makes sense to share development costs with other enterprise business groups that have some requirements and classes in common. Perhaps it might make too much sense. The idea of maximizing an organization's return on investment for a group of related projects, though increasing in the amount of attention given it, has still not taken hold. Organization's hire accountants to look for ways to cut costs and increase profits in most departments and business groups, yet virtually ignore doing the same for software development projects. If you or your fellow developers notice that your efforts are being duplicated by another team, try mentioning this to your project manager. The shared efforts will not only reduce costs and relieve you of perhaps some complex coding efforts, it can also increase your value to your manager. Object-oriented programming offers the best approach for discovering opportunities for sharing development costs. |
|
|
|
|
|
|
|
|
This chapter helped you understand various key issues with regard to developing object-oriented Visual Basic applications in corporate and commercial environments. In particular, you received an overview and discussion of Visual Basic, project management, and the development process, as well as tips on choosing an effective methodology for the system and the project. You also learned the importance of making the methodology decision, as well as rethinking what developer productivity means. You were presented with advice on staffing the Visual Basic project with quality and productivity in mind, choosing better but fewer team members, creating better enterprise teams and developer roles, and confronting the myth about prototypes. |
|
|
|
|
|
|
|
|
Well, I hope you had a very enlightening and effective three weeks of lessons. Learning how to break an application up into major subsystems is a very productive but complex undertaking, so be sure to keep this book handy for future reference when you encounter productivity bottlenecks in your projects. With the powerful lessons on object-oriented programming you received, you're now well ahead in the object technology paradigm shift that is revolutionizing the way we develop software. |
|
|
|
|
|